Skip to main content
Historic England

Conservation area

There is a problem

  • entry-date column must be in YYYY-MM-DD format

Potterne

reference
5573
name
Potterne
designation-date
1981-02-05
document-url
documentation-url
https://www.wiltshire.gov.uk/planning-conservation-areas
geometry
MULTIPOLYGON (((-2.011350 51.328088,-2.011408 51.328081,-2.011386 51.328028,-2.011599 51.327992,-2.011673 51.327971,-2.012454 51.327929,-2.012532 51.327914,-2.012672 51.327919,-2.012677 51.327927,-2.012671 51.327940,-2.012737 51.327874,-2.012348 51.327748,-2.012219 51.327679,-2.011892 51.327435,-2.011667 51.327238,-2.011410 51.327052,-2.011339 51.327011,-2.011316 51.326977,-2.011308 51.326924,-2.011360 51.326912,-2.011432 51.326939,-2.011446 51.326938,-2.011537 51.326918,-2.011552 51.326872,-2.011593 51.326864,-2.011526 51.326741,-2.011163 51.326813,-2.011149 51.326773,-2.011151 51.326733,-2.011171 51.326654,-2.011208 51.326577,-2.011446 51.326273,-2.011463 51.326262,-2.011492 51.326209,-2.011621 51.325796,-2.011938 51.325840,-2.012210 51.325865,-2.012226 51.325846,-2.013104 51.325898,-2.013150 51.325469,-2.013670 51.325578,-2.013708 51.325524,-2.013909 51.325136,-2.013648 51.325079,-2.013676 51.325028,-2.013722 51.324975,-2.013671 51.324958,-2.013701 51.324921,-2.013730 51.324930,-2.013828 51.324817,-2.013780 51.324782,-2.013865 51.324671,-2.013859 51.324661,-2.013977 51.324520,-2.013477 51.324343,-2.013262 51.324308,-2.013248 51.324365,-2.013212 51.324412,-2.012949 51.324601,-2.012798 51.324736,-2.012550 51.324932,-2.012503 51.324960,-2.012432 51.324989,-2.012290 51.325016,-2.012087 51.325008,-2.011944 51.324978,-2.011114 51.324680,-2.010964 51.324649,-2.010781 51.324622,-2.010145 51.324615,-2.009819 51.324662,-2.009431 51.324429,-2.009394 51.324258,-2.009010 51.324259,-2.008849 51.324253,-2.008796 51.324238,-2.008668 51.324231,-2.008328 51.324123,-2.008087 51.324023,-2.007977 51.323988,-2.007983 51.323980,-2.007870 51.323943,-2.007796 51.324050,-2.007824 51.324061,-2.007830 51.324100,-2.008015 51.324162,-2.007927 51.324287,-2.008318 51.324370,-2.008325 51.324571,-2.008338 51.324609,-2.008367 51.324604,-2.008371 51.324616,-2.008427 51.324616,-2.008393 51.324722,-2.008199 51.324856,-2.008161 51.324911,-2.008023 51.325018,-2.007994 51.325072,-2.007648 51.325340,-2.007625 51.325287,-2.007584 51.325264,-2.007465 51.325232,-2.007247 51.325113,-2.007048 51.325032,-2.006961 51.325010,-2.006938 51.324927,-2.006583 51.324892,-2.006610 51.325042,-2.006701 51.325258,-2.006847 51.325681,-2.006344 51.325792,-2.006666 51.326279,-2.006695 51.326372,-2.006937 51.326279,-2.007065 51.326255,-2.007194 51.326244,-2.007397 51.326250,-2.007704 51.326312,-2.007771 51.326347,-2.007729 51.326644,-2.007794 51.326861,-2.007848 51.326926,-2.007942 51.326918,-2.008075 51.326924,-2.008063 51.327022,-2.008101 51.327114,-2.007874 51.327186,-2.007480 51.327263,-2.007508 51.327331,-2.007530 51.327351,-2.007627 51.327391,-2.007738 51.327406,-2.007927 51.327413,-2.008159 51.327406,-2.008196 51.327421,-2.008283 51.327427,-2.008342 51.327402,-2.008423 51.327551,-2.008399 51.327572,-2.008395 51.327590,-2.008565 51.327798,-2.008599 51.327826,-2.008634 51.327810,-2.008738 51.327882,-2.008833 51.327921,-2.008870 51.327955,-2.008993 51.328187,-2.010160 51.327997,-2.010705 51.327935,-2.010803 51.328075,-2.010826 51.328162,-2.011148 51.328130,-2.011350 51.328088)))
point
POINT (-2.009959 51.326077)
notes
No Appraisal document. Documents need to be requested by email to developmentmanagement@wiltshire.gov.uk
organisation
entry-date

entry-date must be a real date

2025-04-01
start-date
1981-02-05
end-date

How to fix this issue

Your dataset is missing the entry-date column.

The Conservation area guidance explains how to fix the issue:

entry-date

The date the record was last updated.

If the entity has never been updated, enter the same date as start-date.

Write in YYYY-MM-DD format.

Example:

2022-12-20

With dates, some data is better than no data, so:

  • 2022 is fine
  • 2022-12 is better
  • 2022-12-20 is brilliant

How to improve Historic England’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL